Integration query builder framework

ABSTRACT

Techniques are described for constructing a query associated with different data sources. In one example, a method includes identifying a particular data source associated with at least one entity. Obtain a set of data source information defining each entities and a set of metadata associated with the particular data source. Then, provide at least a portion of the defined entities for selection associated with the query builder framework for presentation. In response to identifying a selection of a particular entity, the query builder UI provides for presentation a set of attributes associated with the particular selected entity for selection. In response to identifying a selection of a subset of the presented set of attributes, construct a query based on the particular selected entity and the selected subset of the presented set of attributes in a specified query format associated with the custom adapter associated with the particular data source.

CLAIM OF PRIORITY

This application claims priority under 35 USC § 120 to U.S. patentapplication Ser. No. 15/996,824, filed on Jun. 4, 2018, entitled“Integration Query Builder Framework”; the entire contents of which arehereby incorporated by reference.

BACKGROUND

In software integration there can be many services that users andapplications may need to query. Generally, the software integrationprocess can be achieved by using an integration adapter. Most commonintegration adapters are built using the service metadata of the serviceand provide a typing area for the query to be applied. A user needs totraverse the metadata file manually and type the query using a querylanguage specific to the service, which may or may not be common querylanguage such as Structured Query Language (SQL). However, the processcan get complicated, as the number of potential services can bevirtually unlimited with many services having their own query language.

SUMMARY

Implementations of the present disclosure are generally directed toconstructing a query for a service by using a query modeler userinterface (UI). In one example implementation, a computerized methodexecuted by hardware processors can be performed. The example method cancomprise identifying a particular data source associated with at leastone entity. Each of the data sources are associated with a customadapter, the custom adapters associated with a query builder framework.A set of data source information defining each of the entities and a setof metadata associated with the particular data source are obtained.Through a query builder UI associated with the query builder framework,at least a portion of the defined entities for selection are providedfor presentation. In response to identifying a selection of a particularentity via the query builder UI, the set of attributes defined in theset of obtained metadata associated with the particular data source andassociated with the particular selected entity are provided forpresentation via the query builder UI. In response to identifying aselection of a subset of the presented set of attributes via the querybuilder UI, a query is constructed based on the particular selectedentity and the selected subset of the presented set of attributes in aspecified query format associated with the custom adapter and associatedwith the particular data source.

Implementations can optionally include one or more of the followingfeatures. In some instances, the particular data source is identified inresponse to a selection by a user from a plurality of data sources

In some instances, each custom adapter is uniquely generated by adeveloper at design time.

In some instances, when a set of data source information defining eachof the entities and a set of metadata associated with the particulardata source are obtained, a data source URL and a metadata URL areidentified from a user via the query builder UI. The data source URL isassociated with the set of data source information and the metadata URLis associated with the set of metadata associated with the particulardata source. In some of those instances, the set of data sourceinformation from the data source URL and the set of metadata from themetadata URL is obtained via a web-based request.

In some instances, in response to constructing the query, theconstructed query is executed against the particular data source.Further, a query result set is returned responsive to executing theconstructed query via the query builder UI.

In some instances, in response to constructing the query, an editableversion of the constructed query in the specified query format isprovided for presentation via the query builder UI.

In some instances, each custom adapter is associated with a query formatspecific to the associated data source. Based on the custom adapterassociated with the particular data source, a predefined querytranslation format is identified. The identified predefined querytranslation format is applied to the selected entity and the selectedsubset of the presented set of attributes to generate a translated queryin the predefined query translation format. Further, the query based onthe particular selected entity and the selected subset of the presentedset of attributes in the specified query format is constructed.

In some instances, a plurality of predefined query translation formatsare available, where each predefined query translation format isassociated with a query translation key, and each custom adapteridentifies a particular query translation key to be used in constructingqueries for the data source associated with the custom adapter.

In some instances, in response to obtaining the set of metadataassociated with the particular data source, a predefined entity metadatatranslation format is identified based on the custom adapter associatedwith the particular data source. Further, the set of metadata associatedwith the particular data source using the identified predefined entitymetadata translation format associated with custom adapter associatedwith the particular data source is translated.

In some instances, a plurality of predefined entity metadata translationformats are available, where each predefined entity metadata translationformat associated with a metadata translation key, and each customadapter identifies a particular metadata translation key to be used intranslating the set of metadata associated with the particular entity ofthe custom adapter

Similar operations and processes may be performed in a system comprisingat least one process and a memory communicatively coupled to at leastone processor where the memory stores instructions that when executedcause at least one processor to perform the operations. Further, anon-transitory computer-readable medium storing instructions which, whenexecuted, cause at least one processor to perform the operations mayalso be contemplated. In other words, while generally described ascomputer implemented software embodied on tangible, non-transitory mediathat processes and transforms the respective data, some or all of theaspects may be computer implemented methods or further included inrespective systems or other devices for performing this describedfunctionality. The details of these and other aspects and embodiments ofthe present disclosure are set forth in the accompanying drawings andthe description below. Other features, objects, and advantages of thedisclosure will be apparent from the description and drawings, and fromthe claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an example system forconstructing service specific queries using a query builder framework.

FIG. 2 is a block diagram illustrating a simplified view of analternative example system with example components of a query builderframework.

FIG. 3 represents an example flow for constructing a query associatedwith different data sources using an implementation of a query builderframework.

FIG. 4 represents an example flow for defining one or more customadapters used in an implementation of a query builder framework used toconstruct queries associated with different data sources.

FIGS. 5A-5C illustrates an example query builder user interface (UI)associated with an implementation of the query builder framework.

DETAILED DESCRIPTION

The present disclosure describes systems and methods for constructing aspecific query by using a query modeler user interface (UI). Using thedescribed solution, there will be a series of pages guiding the user toconstruct a service specific query. For example, the described solutionprovides a generic framework for providing UI based query modelingcapabilities for different backend services with metadata information.Further, the solution allows the framework to be hooked or otherwiseconnected to existing integration platforms, providing mechanisms fordevelopers to add implementations that can provide entire modelingautomation. The result is a dynamic and interactive UI generated foreach custom integration adapter based on a particular data sourceindicated, where users can construct a detailed query using guided stepsbased on simple selections within the UI.

In the integration platform, the developers often make service calls todifferent backend services to fetch or update records. In addition tofollowing certain protocols, these backend services each demand aspecific query language with which the service is compatible, oralternatively, a particular format within a particular query language.Each service may have their own query language and/or format, while insome instances, certain services may share a common query languageand/or format. For example, some query languages defined for accessinghypertext transfer protocol (HTTP)-based services include:

-   Plain SQL query language-   Specific/custom query language-   Standard HTTP constructs

In some cases, the consumer making a service call to the backend servicehas to construct either the specific query or standard HTTP constructvalues, and uses an HTTP client to call the service. The HTTP clientcall requires the user to be aware of the specifics and requirements ofthe backend services, such as the particular query language, to use theHTTP client. As a result, the integration process can get complicatedwith legacy systems having complex query languages and only a fewtechnical users knowing the specifics of such languages. As provided inthis solution, a query builder framework is provided, using a querybuilder UI that can build the desired query while simplifying thecomplicated process for the developers and users.

The described solution can also guide a user—via the query builder UI—inconstructing a backend specific query when building an integrationadapter. The adapter developer can use the constructed query by settingit into the HTTP client as a parameter and make a service call. Theadapters usually have UI configuration properties which at runtime willmake a service call to a backend.

In some instances, the described solution can also offer developers theability to add new custom integration adapters. The custom adapters takethe user provided values and query when connecting to the backendservice. The query builder framework is wired to the integrationplatform and the custom integration adapters (also referred to as“custom adapters”) for simple and intuitive query construction. Adeveloper can provide the backend service URL to this framework both forgetting the metadata and for executing the actual query against, and thesame developer can provide small implementations for parsing themetadata and reconstructing the specific query. Using this process, aseamless query modeling experience is offered.

The described solution provides a number of advantages over existingquery creation solutions. Without the solution, each service query mustbe either constructed manually based on a defined knowledge of theservice and its requirements, or a specific implementation for eachservice must be provided to the integration platform itself, a solutionthat is not scalable based on the number of backend services being usedand added every day. Further, the typical user may not be a technicaluser with knowledge of a particular service. By providing this solution,users can easily identify and specify the particular entities andattributes to be considered in a particular query, and do not need toknow or research the particular format in which the query is to beprovided. The solution also ensures each service query generated by theframework is a valid query without errors, typos, or syntax-basedissues, which helps the prevention of failures at the production systemduring runtime. As such, the generated query can be used to check theservice for the runtime behavior before deploying to the integrationplatform and later to the production system. Further, the system caninclude user authentication techniques to ensure that any data sourcesto be queries by a user are those with which the user is authorized toview and interact.

Turning to the illustrated implementation, FIG. 1 is a block diagramillustrating an example system 100 for constructing a query associatedwith different data sources using a described query builder UI. Asillustrated in FIG. 1, system 100 is associated with a system forgenerating and using one or more custom adapters 122, wherein eachcustom adapter 122 is associated with a particular data source 124. Eachdata source 124 can be associated with or include one or more entities126, each entity 126 associated with one or more attributes 128. In someinstances, each entity 126 may be a specific table in a database orotherwise associated with the data source 124. In some cases, one tablewithin the data source 124 corresponds to one entity 126. In someinstances, a data source 124 may be associated with a single entity 126,while other data sources 124 may be associated with a plurality ofentities 126. The data source 124, entity 126, and attribute 128 can bestored remotely at one or more data sources 170 (and stored as entities172 and attributes 174, as illustrated). The data source 124 mayidentify the remote data source 170, and entity 126 and attribute 128information may be obtained from the data source 170 via network 140.

In general, the illustrated system 100 can incorporate a plurality ofsystems to perform and use the custom adapters 122 to generateeasy-to-build queries, including a backend system 102, one or moreclients 150, and one or more data sources 170, and can allow theillustrated components to share and communicate information acrossdevices and systems (e.g., via network 140). In some instances, at leastsome or all of the components may be cloud-based components orsolutions, as well as web services, while in others, non-cloud-basedsystems may be used. In some instances, non-cloud-based systems, such ason-premise systems, may use or adapt the processes described herein.Although components are shown individually, in some implementations,functionality of two or more components, systems, or servers may beprovided by a single component, system, or server.

As used in the present disclosure, the term “computer” is intended toencompass any suitable processing device. For example, backend system102 and client 150 may be any computer or processing device such as, forexample, a blade server, general-purpose personal computer (PC), Mac®,workstation, UNIX-based workstation, or any other suitable device.Moreover, although FIG. 1 illustrates a single backend system 102, thesystem 100 can be implemented using a single system or more than thoseillustrated, as well as computers other than servers, including a serverpool. In other words, the present disclosure contemplates computersother than general purpose computers, as well as computers withoutconventional operating systems. Similarly, the client 150 may be anysystem which can request data and/or interact with the backend system102. The client 150, in some instances, may be a desktop system, aclient terminal, or any other suitable device, including a mobiledevice, such as a smartphone, tablet, smartwatch, or any other mobilecomputing device. In general, each illustrated component may be adaptedto execute any suitable operating system, including Linux, UNIX,Windows, Mac OS®, Java™, Android™, Windows Phone OS, or iOS™, amongothers.

In general, the backend system 102 may be associated with the executionof one or more backend or business applications, including a querybuilder framework 108 and its associated functionalities. In someinstances, the backend system's 102 primary functionality may relate toactions associated with the construction of a query as described herein,including the defining and management of one or more custom adapters 122associated with particular data sources 124, and which are used togenerate queries specific to particular entities 126 and theirattributes 128. The one or more custom adapters 122 may include a set ofquery translation data 130 and a set of metadata translation data 132,where those sets of translation data provide an indication to the querybuilder framework 108 how to interpret metadata associated with thecorresponding data source 124, as well as how to construct a querydirected to the data source. In some instances, the custom adapter 122may identify a particular query translation key (corresponding to querytranslation key 142) and a metadata translation key (corresponding tometadata translation key 146). When using the custom adapter 122, thosekeys may be used to identify a separate translation (either querytranslation 140 or metadata translation 144. The custom adapter 122 mayalso include a stored version of a data source URL 134 and/or a metadataURL 136, where those URLs provide links or references to the associateddata source 124 itself, or a URL associated with the data source'smetadata (e.g., metadata 176) of the corresponding data source 170.

In some instances, the backend system 102 may be associated with anend-to-end business solution system, enterprise resource planning (ERP)systems, customer resource management (CRM) systems, businessintelligence systems, cloud platform systems, supplier management (SM)systems, or any other suitable system, including non-business-relatedsystems. In general, the backend system 102 executes at least a querybuilder framework 108, which can be interacted with by one or moreclient applications 156, and can access data from or provide access todata from one or more data sources 170.

The illustrated query builder framework 108 is used to manage and usethe custom adapters 122 to generate one or more queries. To support thequery construction solution described herein, each custom adapter 122identifies an associated data source 124. In some instances, the customadapter 122 may store or otherwise have reference to the particularentities 126 associated with the data source 124. In others, thoseentities 126 may be retrieved or otherwise identified in response to arequest to build or construct a query associated with the particulardata source 170. The entity 172 can include but is not limited to adatabase table or combination of tables (e.g., a union or join of two ormore tables, database projections or views), database schema, ordatabase system. The attributes 128 can represent columns or datainformation of the entity 126/172. Each custom adapter 122 can containor identify query translation data 130 that specifically defines aparticular query translation for the data source 124. In otherinstances, the query translation data 130 can be a unique identifierused to link the particular custom adapter 122 to a particular querytranslation 140 stored in the translation store 138 (e.g., via aparticular key 142). The metadata translation data 132 can specificallydefine a particular metadata translation identifying one or moreoperations necessary to interpret the metadata of the associated datasource 124. In other instances, the metadata translation data mayreference or link to a unique identifier used to link the particularcustom adapter 122 to a particular metadata translation 144 in thestored translation store 138. The one or more query translations 140 andone or more metadata translations 144 can be a programmingimplementation adhering to the framework contract. In some instance ofthe implement, the query builder framework 108 identifies the datasource URL 134 and the metadata URL 136 that are provided from the user.The data source URL 134 can be used to obtain or retrieve theinformation from a data source for a query construction, and themetadata URL 136 can be used to obtain or retrieve the information for ametadata associated with the particular data source in order to identifyparticular entities and attributes associated with the data source 170.

The translation store 138 can hold, store, or reference the particulartranslations used to understand and interact with particular datasources 170. In some instances, such as where one or more querytranslations 140 are provided for different services, including thoseservices supporting or otherwise requiring a specific query language, anobject reference of the implementation will be held by the store, thereferences associated with a key 142 or other unique identifiersassociated with the translation requirements. The correspondingidentifier can be associated with the custom adapter 122, so that theproper translation can be used in constructing the query. Thetranslation store 138 can also store one or more metadata translations144, where the metadata translations 144 are associated with particulardata sources 124 and are used to parse or process metadata associatedwith a service. In some instances, particular metadata translations 144can be associated with a key 146 or other unique identifiers associatedwith the metadata translation of one or more services or data sources.The corresponding identifier can be associated with one or more customadapters 122 and used to interpret and interact with the metadata 176 ofthe corresponding data sources 170. The query translations 140 representthe custom implementations of the query translator contract, and themetadata translations 144 represent the custom metadata translationimplementations of different services. In some instances, one or more ofthe custom adapters 122 may identify a particular metadata translationkey 146 to be used in translating the set of metadata associated withthe particular entity 126.

Returning to the query builder framework 108, the framework 108 isillustrated as including five components: a query construct manager 110,a query translator 112, a metadata translator 114, a query builder UI116, and a query execution manager 118. Some or all of the componentsmay be combined into a single component or the query builder framework'sinherent functionality, while portions of the solution may also beseparated into different and/or external components and variousapplications, agents, and/or other software. In general, the querybuilder framework 108 is used to create the query builder UI 116 usingthe service metadata associated with a data source 124 corresponding toa particular custom adapter 122. The various illustrated components maybe used in combination to provide the described functionality, whileother implementations may include more or different components toperform the various operations.

The query construct manager 110 is a central component used toorchestrate or manage the other components, such as the query translator112, the metadata translator 114, the query builder UI 116, and thequery execution manager 118. In some instances, the query constructmanager 110 can be responsible for creating a query modeler UI, whichcan be used by a developer to create a custom adapter 122 to be usedlater. Along with the query execution manager 118, the query constructmanager 110 can take the constructed query and initiate the execution ofthe query against the data source 170 using the constructed query.

The query translator 112 can perform one or more different customimplementations provided by a developer for supporting services using aspecific query language. The query translator 112 can access theinformation defining how a particular query is to be formatted (e.g.,the particular query translation 140), and can ensure that the inputtypes, sequence, and syntax of the constructed query matches the definedrequirements of the data source 170 associated with a particular query.

The metadata translator 114 can perform one or more different customimplantations provided by a developer for parsing and interpretingmetadata 176 information retrieved from a particular data source 170. Inparticular, the metadata translator 114 can identify and apply aparticular metadata translation 144 (e.g., as defined or referenced by aparticular custom adapter 122) to a set of obtained metadata 176 of thedata source 170.

The query builder UI 116 can be defined to generate and manage a userinterface containing the UI pages and visualizations used to build andconstruct the query. The query builder UI 116 can present informationabout a particular data source 170, its various entities 172, andattributes 174 associated with those entities 172 to users in order toobtain or gather information from corresponding user input (e.g., viaGUI 158 of the client 150), and use that information in connection withthe other components to determine how to generate a particular querywith an associated data source 170. In some instances of theimplementation, the query builder UI 116 is generated by the queryconstruct manager 110. The query builder UI 116 can provide a series ofpages or screens that guide users in constructing service specificqueries. In some instances, users may initially identify a particulardata source 170 to be associated with the query. In response toidentifying the data source 170, the query builder UI 116 and the queryconstruct manager 110, among others, can be used to identify the customadapter 122 associated with the identified data source 170 (via theassociated data source 124 definition), and can present a set ofentities 172 associated with the selected data source 170. Based on theselected entity, the query builder UI 116 can then present a set ofattributes 174 corresponding to the selected entity, allowing users toselect particular attributes to be included in the constructed query. Insome instances, additional information or parameters may be added viathe query builder UI 116, such as providing a request on how resultsshould be ordered, filtered, sorted, or otherwise presented. Afterconstructing the query via the query builder UI 116, the query executionmanager 118 can be used to execute the constructed query against theservice of the data source 170. The results of the query execution canbe returned, and, in some instances, can be presented via the querybuilder UI 116. In some instances, prior to executing the constructedquery, the query builder UI 116 may allow users to interact with andmodify the constructed query. For example, additional parameters andinformation can be added or removed from the constructed query prior toactually executing the query. In such instances, users can be providedwith a constructed query in the correct format, and can modify theconstructed query into a fine-tuned or otherwise modified query withoutaffecting the syntax or format requirements of the data source 170.

As illustrated, the backend system 102 includes interface 104, processor106, the query builder framework 108, and memory 120. The interface 104is used by the backend system 102 for communicating with other systemsin a distributed environment—including within the environment100—connected to the network 140, e.g., one or more clients 150 and datasources 170, among others, as well as other systems communicably coupledto the illustrated backend system 102 and/or network 140. Generally, theinterface 104 comprises logic encoded in software and/or hardware in asuitable combination and operable to communicate with the network 140and other components. More specifically, the interface 104 may comprisesoftware supporting one or more communication protocols associated withcommunications such that the network 140 and/or interface's hardware isoperable to communicate physical signals within and outside of theillustrated environment 100. Still further, the interface 104 may allowthe backend system 102 to communicate with one or more clients 150 toreceive particular queries and information requests, as well as toreceive updates or interactions with the custom adapters 122 via clientapplication 156 and/or from one or more data sources 170, as describedin the present disclosure.

Network 140 facilitates wireless or wireline communications between thecomponents of the environment 100 (e.g., between the backend system 102and a particular client 150), as well as with any other local or remotecomputer, such as additional devices, clients (e.g., client 150),servers, or other devices communicably coupled to network 140, includingthose not illustrated in FIG. 1. In the illustrated environment, thenetwork 140 is depicted as a single network, but may be comprised ofmore than one network without departing from the scope of thisdisclosure, so long as at least a portion of the network 140 mayfacilitate communications between senders and recipients. In someinstances, one or more of the illustrated components (e.g., the backendsystem 102, and data sources 170, among others) may be included withinnetwork 140 as one or more cloud-based services or operations. Thenetwork 140 may be all or a portion of an enterprise or secured network,while in another instance, at least a portion of the network 140 mayrepresent a connection to the Internet. In some instances, a portion ofthe network 140 may be a virtual private network (VPN). Further, all ora portion of the network 140 can comprise either a wireline or wirelesslink. Example wireless links may include 802.11a/b/g/n/ac, 802.20,WiMax, LTE, and/or any other appropriate wireless link. In other words,the network 140 encompasses any internal or external network, networks,sub-networks, or combination thereof operable to facilitatecommunications between various computing components inside and outsidethe illustrated environment 100. The network 140 may communicate, forexample, Internet Protocol (IP) packets, Frame Relay frames,Asynchronous Transfer Mode (ATM) cells, voice, video, data, and othersuitable information between network addresses. The network 140 may alsoinclude one or more local area networks (LANs), radio access networks(RANs), metropolitan area networks (MANs), wide area networks (WANs),all or a portion of the Internet, and/or any other communication systemor systems at one or more locations.

The backend system 102 also includes one or more processors 106.Although illustrated as a single processor 106 in FIG. 1, multipleprocessors may be used according to particular needs, desires, orparticular implementations of the environment 100. Each processor 106may be a central processing unit (CPU), an application specificintegrated circuit (ASIC), a field-programmable gate array (FPGA), oranother suitable component. Generally, the processor 106 executesinstructions and manipulates data to perform the operations of thebackend system 102, in particular those related to the query builderframework 108. Specifically, the processor(s) 106 executes thealgorithms and operations described in the illustrated figures, as wellas the various software modules and functionality, including thefunctionality for sending communications to and receiving transmissionsfrom clients 150 and other illustrated components, as well as to otherdevices and systems. Each processor 106 may have a single or multiplecore, with each core available to host and execute an individualprocessing thread. In particular, processor 106 can be used to executethe query builder framework 108 described previously and itsfunctionality. In some instances, one or more of the components of thequery builder framework 108 may be executed remotely by one or moreremote processors 106, as well.

Regardless of the particular implementation, “software” includescomputer-readable instructions, firmware, wired and/or programmedhardware, or any combination thereof on a tangible medium (transitory ornon-transitory, as appropriate) operable when executed to perform atleast the processes and operations described herein. In fact, eachsoftware component may be fully or partially written or described in anyappropriate computer language including C, C++, JavaScript, Java™,Visual Basic, assembler, Perl®, any suitable version of 4GL, as well asothers.

Memory 120 of the backend system 102 may represent a single memory ormultiple memories. The memory 120 may include any memory or databasemodule and may take the form of volatile or non-volatile memoryincluding, without limitation, magnetic media, optical media, randomaccess memory (RAM), read-only memory (ROM), removable media, or anyother suitable local or remote memory component. The memory 120 maystore various objects or data (e.g., one or more custom adapters 122 andany associated data source 124, query translation data 130, metadatatranslation data 132, data source URL 134, and metadata URL 136, as welltranslation store 138, as well as others, etc.), including financialdata, user information, administrative settings, password information,caches, applications, backup data, repositories storing business and/ordynamic information, and any other appropriate information associatedwith the backend system 102 including any parameters, variables,algorithms, instructions, rules, constraints, or references thereto.Additionally, the memory 120 may store any other appropriate data, suchas VPN applications, firmware logs and policies, firewall policies, asecurity or access log, print or other reporting files, as well asothers. While illustrated within the backend system 102, some or all ofmemory 120 may be located remote from the backend system 102 in someinstances, including as a cloud application or repository, or as aseparate cloud application or repository when the backend system 102itself is a cloud-based system. Further, at least some of memory 120 maybe associated with data or information located at one or more remotedata sources 170. That data may be accessed at the data sources 170 andused in the described processes, and the related data may, in someinstances, be stored in memory 120 for local use. In some instances, atleast a portion of the accessed data from the data sources 170 may bepersisted locally in memory 120, such as in a cache or other localstorage to reduce network resources and increase the speed of dataaccess and availability.

As illustrated and described, one or more clients 150 may be present inthe example system 100. Each client 150 may be associated with requeststransmitted to the backend system 102 related to the client application156 executing on or at the client 150, including those related toqueries constructed via the query builder framework 108, as well as torequests to view or visualize particular entities 172 and queriessubmitted to access at least a portion of the entity 172. Differentclients 150 may interact with different custom adapters 122 via thequery builder framework 108 and the query execution manager 118, wherethe query execution manager 118 and the query builder UI 116 are used todetermine how and what to provide in response to the received userselections.

As illustrated, each client 150 may include an interface 152 forcommunication (similar to or different from interface 104), at least oneprocessor 154 (similar to or different from processor 106), the clientapplication 156, memory 160 (similar to or different from memory 120),and a graphical user interface (GUI) 158.

The illustrated client 150 is intended to encompass any computing devicesuch as a desktop computer, laptop/notebook computer, mobile device,smartphone, personal data assistant (PDA), tablet computing device, oneor more processors within these devices, or any other suitableprocessing device. In general, the client 150 and its components may beadapted to execute any operating system, including Linux, UNIX, Windows,Mac OS®, Java™, Android™, or iOS. In some instances, the client 150 maycomprise a computer that includes an input device, such as a keypad,touch screen, or other device(s) that can interact with the clientapplication 156, and an output device that conveys informationassociated with the operation of the applications and their applicationwindows to the user of the client 150. Such information may includedigital data, visual information, or a GUI 158, as shown with respect tothe client 150. Specifically, the client 150 may be any computing deviceoperable to communicate queries or communications to the backend system102, other clients 150, and/or other components via network 140, as wellas with the network 140 itself, using a wireline or wireless connection.In general, client 150 comprises an electronic computer device operableto receive, transmit, process, and store any appropriate data associatedwith the environment 100 of FIG. 1.

Client application 156 may be any suitable application, program, mobileapp, or other component. As illustrated, the client application 156interacts with the backend system 102 to perform queries and otherdatabase and/or table-related operations via query builder framework108. In some instances, the client application 156 may be a browser,where the functionality of the client application 156 may be realizedusing a web application or website the user can interact with via theclient application 156. In other instances, the client application 156may be a remote agent, component, or client-side version of the backendsystem 102, or another application, which can interact with the customadapters 122 via the query builder framework 108. In some instances, theclient application 156 may interact directly with the backend system102.

In some instances, the client application 156 may be programmed toinitiate change detection algorithms on its own, even without submittinga new query to the backend system 102. In some instances, the clientapplication 156 may be able to communicate with the query constructmanager 110, such as by calling the query execution manager 118 via aparticular application programming interface (API) or other method, andreceiving system values from the user. If a request is received, theclient application 156 may be able to trigger a new query generation toreceive a set of data from the associated data source 124 included inthe custom adapters 122.

GUI 158 of the client 150 interfaces with at least a portion of theenvironment 100 for any suitable purpose, including generating a visualrepresentation of the client application 156 and/or the contentassociated with the client application 156 and, in some cases, resultsor portions of the custom adapters 122. In particular, the GUI 158 maybe used to present screens or UIs associated with the client application156. In some instances, those screens or UIs may include buttons orother interactive elements allowing users to initiate a request for arefresh, or to perform actions within the application 156 which mayresult in a query to the backend system 102. GUI 158 may also be used toview and interact with various Web pages, applications, and Web serviceslocated local or external to the client 150. Generally, the GUI 158provides the user with an efficient and user-friendly presentation ofdata provided by or communicated within the system. The GUI 158 maycomprise a plurality of customizable frames or views having interactivefields, pull-down lists, and buttons operated by the user. For example,the GUI 158 may provide interactive elements that allow a user to viewor interact with information related to the operations of processesassociated with the backend system 102, including the presentation ofand interaction with particular entity 126 included in the one or morecustom adapters 122. In general, the GUI 158 is often configurable,supports a combination of tables and graphs (bar, line, pie, statusdials, etc.), and is able to build real-time portals, applicationwindows, and presentations. Therefore, the GUI 158 contemplates anysuitable graphical user interface, such as a combination of a genericweb browser, a web-enable application, intelligent engine, and commandline interface (CLI) that processes information in the platform andefficiently presents the results to the user visually.

FIG. 1 further includes one or more data sources 170, which may be oneor more external and/or cloud-based data sources 170 storing one or moreentities 172 with one or more attributes 174 and a metadata information176. The entities 172 may be standalone tables, or such tables may beincorporated with or a part of a join to one or more of the customadapters 122 in backend system 102. In some instances, the data sources170 can feed data information to the custom adapters 122 via the querybuilder framework 108 and its query construct manager 110, while inother instances the data sources 170 can update the custom adapters 122in other manners.

While portions of the elements illustrated in FIG. 1 are shown asindividual modules that implement the various features and functionalitythrough various objects, methods, or other processes, the software mayinstead include a number of sub-modules, third-party services,components, libraries, and such, as appropriate. Conversely, thefeatures and functionality of various components can be combined intosingle components as appropriate.

FIG. 2 is a block diagram illustrating an example system with componentsof the query builder framework. As illustrated in FIG. 2, system 200 isassociated with or connected to at least one HTTP based service 220 forintegration into the query builder framework and for constructingqueries directed to the service and its data. The illustrated system 200represents a simplified version of system 100 including severaladditional specific components. Other implementations of system 200 canbe implemented using separate or alternative components instead.

As illustrated, system 200 includes a query builder framework 202 andone or more clients 250 communicably connected via network 240. Theclient 250 may be any computer or system attempting to query or accessthe entities 272 referenced by the query construct manager 204 usingservice calls or methods as defined within the system 200. Thecomponents described in FIG. 2 may be similar to or different from thecomponents described in FIG. 1. For example, the query builder framework202, the query construct manager 204, the query translator store 206,metadata translator store 210, and query builder UI 214 may be similarto or different from query builder framework 108, query constructmanager 110, the query translator 112, metadata translator 114, andquery builder UI 116 of FIG. 1. The one or more clients 250 may begenerally similar to or different from the one or more clients 150 ofFIG. 1, and are shown in a simplified manner for purposes of thediscussion related to FIG. 2.

The query construct manager 204 (which may be similar to or differentfrom the query construct manager 110 in query builder framework 108) canbe used to orchestrate or manage the other components, such as the querytranslator store 206, the metadata translator store 210, and the querybuilder UI 214. In some instances, the query construct manager 204 canbe responsible for creating a query modeler UI and take the constructedquery and initiate the execution of the query against the data source270 using the constructed query. In some instances, the query constructmanager 204 can receive or obtain the service metadata from the HTTPservice 220 by accessing the set of metadata 276 and using thatinformation to determine the specific entities and attributes of thedata source 270. In other words, a particular data source 270, the datasource entity information 272 information, and the data source metadatainformation 276 may be accessible by the query construct manager 204through the HTTP based service 220.

In some instances, one or more specific query translators 208 may bemanually or automatically associated with a query translator store 206.The specific query translators 208 can be stored in or accessible to thequery translator store 206, such that the set of the query translationformats can be applied to the particular data sources 270 and theirassociated entities 272 when constructing a query through the describedprocesses. In some instances, a particular data source 270 or itsentities 272 may be associated with a query translation key (which canbe stored with local information associated with the data source 230,e.g., at a custom adaptor stored in or associated with the query builderframework 202), where certain query translators 208 are also associatedwith those specific keys. Using the identified key, the specific querytranslator 208 associated with a data source 270 can be identified,accessed, and used to generate any future queries based on one or moreuser selections, where the translators 208 allow the query to begenerated in a format and/or syntax corresponding to the requirements ofthe data source 270. When a particular data source is identified via thequery builder UI 214, the query construct manager 204 can transform orassociate the specific query translator 208 to the associated querytranslator key 232 for use in constructing the queries. In someinstances, a data source URL may be received via the query builder UI214, which can then be used to identify a particular data source 270upon which the query is to be executed. Using that information, thequery construct manager 204 can access, via the HTTP based service ordirectly from the data source 270, the entity data 272, the attributedata 274, and the metadata data 276.

Additionally, one or more specific metadata translators 212 may bemanually or automatically associated with a metadata translator store210. The specific metadata translators 212 can be stored in the metadatatranslator store 210, such that the set of the metadata translationformats can be applied to the associated data sources 270 containing thecorresponding metadata translator key 234 as queries are received. Inthis instance, a metadata URL is received via the query builder UI 214,the query construct manager 204 can identify the associated data source270 using the metadata information.

The data sources 270 can be accessed by the query construct manager 204through the HTTP based service 220 with the corresponding identifiedmetadata information 276. The HTTP based service 220 can be a HTTPclient server or servers that may be provided by a single or multiplecomponents and systems. In some instances, the languages used to accessthe HTTP based service 220 can include, but are not limited to, astandard SQL query language, a custom SQL or other query language, orstandard HTTP constructs, among others.

The client 250 can interact with the query builder UI 214 and queryconstruct manager 204 via network 240. The client 250 may be anysuitable computer or system associated with a user or applicationauthorized to interact with the data sources 270 and their associatedentities 272. In some instances, the client 250 may have a userinterface 252 through which a query builder UI is provided (via thequery builder UI 214 component) that guides the user through a queryconstruction process. Through the user interface 252, users can identifya particular data source 270 to be queries. Based on the selected datasource 270, the query construct manager 204 can determine the entities272 associated with the data source 270 and make those selectable by theuser. In response to receiving a selection of a particular entity orentities 272, the attributes 274 corresponding to those entities 272 canbe selected in a next screen or presentation. Once those attributes 274are selected, along with any other appropriate information, the queryconstruct manager 204 can construct a query based on those selectionsand the specific formatting requirements of the data source 270. Theresulting query can be presented to the user interface 252 for review,edits, and execution. In some instances, the query construct manager 204can automatically execute the constructed query against the data source270 once the selections are made.

FIG. 3 represents an example flow 300 for constructing a queryassociated with different data sources. For clarity of presentation, thedescription that follows generally describes method 300 in the contextof the system 100 illustrated in FIG. 1. However, it will be understoodthat method 300 may be performed, for example, by any other suitablesystem, environment, software, and hardware, or a combination ofsystems, environments, software, and hardware as appropriate.

At 305, a particular data source associated with at least one entity isidentified. The particular data source can be identified in response toa user selection from a plurality of data sources presented via a querybuilder UI, or in response to an action (by the user or an application)otherwise determining that a query associated with the particular datasource is to be constructed using the present solution. In someinstances, the particular data source is selected by the user from thequery builder UI, and the selected data source is passed to the querybuilder framework to identify a custom adapter associated with that datasource. Using the custom adapter, information about how to generate aquery for the data source may be available to the query builderframework, and can be used to construct an appropriate query.

At 310, a set of data source information defining at least one entityincluded in or associated with the particular data source and a set ofmetadata associated with the particular data source can be obtained bythe backend system. The data source information and the metadata may beavailable or associated with the custom adapter corresponding to thedata source, or information on how to access the data source to obtainthe information may be provided. The data source information, includingthe set of metadata information, can be used to understand the datasource and determine how the query is to be constructed, as well as theoptions available to users via the query builder UI. In some instances,the set of data source information is associated with the data sourceURL, and the set of metadata associated with the particular data sourceis associated with the metadata URL. Further, the set of data sourceinformation from the data source URL and the set of metadata from themetadata URL can be obtained via a web-based request. In anotherinstance, the data source information may be associated with one or moretranslations used to interpret the metadata associated with the datasource. The metadata translations may be associated with or identifiedby a unique identifier, which can be accessed from a metadatatranslation store and used to interpret the metadata associated with thedata source.

At 315, in response to obtaining the set of data source information aquery builder UI associated with the query builder framework can beprovided for presentation. In doing so, at least a portion of theentities associated with the data source may be made available forselection. In some instances, a first window or application screen ofthe query builder UI may be used for the selection of the associatedentities. The associated entities can correspond to or be a subset ofthe set of data source information previously obtained.

At 320, a selection of a particular entity is identified via the querybuilder UI. At 325, in response to identifying a selection of aparticular entity via the query builder UI, a set of attributesassociated with the particular entity can be identified and provided forpresentation to the query builder UI. The set of attributes may bedetermined based on the set of metadata associated with the particulardata source and associated with the particular selected entity. In someinstances, after the user selects the entity and navigates from thefirst window or application screen, the query builder UI may have asecond window or application screen to display options for selecting theattributes associated with the selected entity. In some instances, thefirst window or application screen may be adapted or dynamicallymodified to present the available attributes without moving to a secondwindow or application screen. In addition to, or after the selection ofthe attributes, additional information may be selectable by the user viathe query builder UI. For example, a particular presentation parametermay be available that allows the user to select how the results of theconstructed query will be presented, such as an order by information, aswell as other display-related options. Further, additional query-relatedoptions and parameters may be defined via the query builder UI, such asadding additional restrictions or filters on the information to bepresented.

At 330, a selection of a subset of the presented set of attributes isidentified via the query builder UI. At 335, in response to identifyinga selection of a subset of the presented set of attributes via the querybuilder UI, a query based on the particular selected entity and theselected subset of the presented set of attributes is constructed in aspecific query format associated with and/or defined by the customadapter of the particular data source. Specifically, the specific queryformat associated with the data source can be applied to the selectedentity and the selected attributes to generate a query that meets theformat and syntax requirements of the data source. In some instances,the constructed query can be executed against the particular data sourceand can return the query results to the query builder UI. In someinstances, the constructed query can be provided for presentation to thequery builder UI for review by the user. In those instances, the querybuilder UI may allow users to interact and edit the constructed query,allowing tweaks and changes to the query, as well as further restrictionand/or parameters to be manually added to the query prior to execution.

FIG. 4 represents an example flowchart 400 for defining the customadapters used in generating queries associated with particular datasources. FIG. 4 can be executed at any suitable time, including duringor after the operations described in FIG. 3. Moreover, it will beunderstood that method 400 may be performed, for example, by any othersuitable system, environment, software, and hardware, or a combinationof systems, environments, software, and hardware as appropriate.

At 405, a particular data source associated with at least one entity isidentified as a data source upon which a custom adapter is to becreated. The particular data source may be identified by a developercreating and defining a custom adapter for one of a plurality of datasources. In some instances, the particular identified data source isselected by a developer having particular knowledge of the data source,as well as the specific query format used and required by the datasource. The custom adapter, once generated, can be used by a querybuilder framework for user-defined queries created using a query builderUI that allows non-technical users (or other users without the knowledgeor time to determine the particular requirements of a data source) todefine queries for the particular data source based on the data source'smetadata and available entities in a simple and streamlined manner. Thedata source may store or be associated with the information needed by aquery builder framework that is used to generate a query in a requiredformat.

At 410, in response to the creation of the custom adapter, an indicationof a query translation format associated with the particular data sourceis identified. The query translation format can be used to manipulateand format the selected entities and attributes, and any other relevantinformation, into a format required for the data source. The querytranslation format can be identified by the developer, and may be analready-used format (e.g., by one of the other data sources previouslyassociated with another custom adapter) or in a new format that may needto be defined. In some instances, the custom adapter, in response to theidentification of the query translation format, may be associated with aunique query translation key. That key can then be used to access theparticular query translation indicated at runtime. In doing so, theformat can be shared by multiple custom adapters. Formats already usedcan be selected from the available formats, while new formats may needadditional definition and the assignment of a unique key for futuredescription.

At 415, metadata information associated with the particular data sourceis identified. In some instances, the metadata information includes anindication of how metadata from the data source is to be interpreted. Asdifferent data sources may have different formats for their metadata,the metadata translation format can be used in future interactions withthe data source to successfully interpret and understand the metadata.In some instances, the metadata translation data may be shared by one ormore data sources. That translation data may be associated with a uniqueidentifier and stored in the custom adapter for the data source, wherethe unique identifier references or links to a particular metadatatranslation to be applied. In some instances, the identified metadatainformation may identify the particular location at which the metadatacan be accessed, such as a specific URL or other link storing themetadata.

At 420, the custom adapter is persisted for future use via the querybuilder UI. In some instances, the custom adapter is generated by adeveloper at design time. The developer can add custom adaptersassociated with a particular data source and in an implementation of aquery builder framework to the integration platform. As such, thepersisted custom adapter can take the user provided values and query viathe query builder UI when connecting to the backend service in order toconstruct the specific query.

FIGS. 5A-5C illustrate an example implementation of a graphical userinterface associated with the query builder framework and the querybuilder UI. As illustrated in FIG. 5A, a window or an application screenof the query builder UI 500A includes the option for the user to selectan entity associated with a particular data source 170. Once the userselects the entity from the dropdown list, the user can navigate to thefollowing screen by clicking on the next button.

FIG. 5B illustrates the graphical user interface that the user navigatesto after clicking the next button in the previous query builder UIscreen 500A. In this window or application screen, the user can select aset of attributes (e.g., ID, name, price, location, and size, as well asother attributes) associated with the previously selected entity. In theillustrated example, an option to select an order by capability isincluded in the UI screen 500B, where the option allows users toindicate how a query result will be ordered. The selection can be addedto the constructed query along with the selected entity and attributes.The operations available to the user can include order by, group by, andwhere, as well as others.

In FIG. 5C, the adapter configuration UI 500C illustrates the inputfields for the user to enter a data source URL corresponding to the datasource and a metadata URL for retrieving the metadata informationassociated with the data source. In some instances, this information maybe available and populated from the custom adapters. When the userclicks the build button, the generated query will be displayed in thefield that corresponds to the query title field. In someimplementations, the adapter configuration UI 500C can communicate withthe query builder framework 108 by using a custom query translator 112.

Implementations of the subject matter described in this specificationcan be implemented in a computing system that includes a back-endcomponent, for example, as a data server, or that includes a middlewarecomponent, for example, an application server, or that includes afront-end component, for example, a client computer having a graphicaluser interface or a Web browser through which a user can interact withan implementation of the subject matter described in this specification,or any combination of one or more such back-end, middleware, orfront-end components. The computing system can include clients andservers. A client and server are generally remote from each other andtypically interact through a communication network. The relationship ofclient and server arises by virtue of computer programs running on therespective computers and having a client-server relationship to eachother.

In some implementations, any or all of the components of the computingsystem, both hardware or software (or a combination of hardware andsoftware), may interface with each other or the interface using an APIor a service layer (or a combination of API and service layer). The APImay include specifications for routines, data structures, and objectclasses. The API may be either computer language independent ordependent and refer to a complete interface, a single function, or evena set of APIs. The service layer provides software services to thecomputing system. The functionality of the various components of thecomputing system may be accessible for all service consumers using thisservice layer. Software services provide reusable, defined businessfunctionalities through a defined interface. For example, the interfacemay be software written in JAVA, C++, or other suitable languageproviding data in XML format or other suitable format. The API orservice layer (or a combination of the API and the service layer) may bean integral or a stand-alone component in relation to other componentsof the computing system. Moreover, any or all parts of the service layermay be implemented as child or sub-modules of another software module,enterprise application, or hardware module without departing from thescope of this disclosure.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinvention or on the scope of what may be claimed, but rather asdescriptions of features that may be specific to particularimplementations of particular inventions. Certain features that aredescribed in this specification in the context of separateimplementations can also be implemented in combination in a singleimplementation. Conversely, various features that are described in thecontext of a single implementation can also be implemented in multipleimplementations separately or in any suitable sub-combination. Moreover,although features may be described earlier as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Particular implementations of the subject matter have been described.Other implementations, alterations, and permutations of the describedimplementations are within the scope of the following claims as will beapparent to those skilled in the art. While operations are depicted inthe drawings or claims in a particular order, this should not beunderstood as requiring that such operations be performed in theparticular order shown or in sequential order, or that all illustratedoperations be performed (some operations may be considered optional), toachieve desirable results. In certain circumstances, multitasking orparallel processing (or a combination of multitasking and parallelprocessing) may be advantageous and performed as deemed appropriate.

Moreover, the separation or integration of various system modules andcomponents in the implementations described earlier should not beunderstood as requiring such separation or integration in allimplementations, and it should be understood that the described programcomponents and systems can generally be integrated together in a singlesoftware product or packaged into multiple software products.

Accordingly, the earlier description of example implementations does notdefine or constrain this disclosure. Other changes, substitutions, andalterations are also possible without departing from the spirit andscope of this disclosure.

Furthermore, any claimed implementation described later is considered tobe applicable to at least a computer-implemented method; anon-transitory, computer-readable medium storing computer-readableinstructions to perform the computer-implemented method; and a computersystem comprising a computer memory interoperably coupled with ahardware processor configured to perform the computer-implemented methodor the instructions stored on the non-transitory, computer-readablemedium.

The invention claimed is:
 1. A computer-implemented method comprising:identifying a particular data source associated with at least oneentity, each data source associated with a custom adapter associatedwith a query builder framework, wherein each of the at least oneentities is associated with one or more attributes; obtaining a set ofdata source information defining each of the at least one entities and aset of metadata associated with the particular data source; providingfor presentation, via a query builder user interface (UI) associatedwith the query builder framework, at least a portion of the at least onedefined entities for selection by a user; in response to identifying aselection of a particular entity via the query builder UI, providing forpresentation, via the query builder UI, a set of attributes associatedwith the particular selected entity for selection by the user, whereinthe set of attributes are determined based on the set of obtainedmetadata associated with the particular data source and associated withthe particular selected entity; and in response to identifying aselection of a subset of the presented set of attributes via the querybuilder UI by the user, constructing a query based on the particularselected entity and the selected subset of the presented set ofattributes in a specified query format associated with the customadapter associated with the particular data source, wherein the customadapter includes a set of query translation data providing the querybuilder framework with instructions on how to construct the querydirected to the particular data source, and wherein the specified queryformat is applied to the particular selected entity and the selectedsubset of the presented set of attributes to generate the query thatmeets format and syntax requirements of the data source.
 2. The methodof claim 1, wherein the particular data source is identified in responseto a selection by the user from a plurality of data sources.
 3. Themethod of claim 1, wherein each custom adapter is associated with aquery format specific to the associated data source, and whereinconstructing the query based on the particular selected entity and theselected subset of the presented set of attributes in the specifiedquery format comprises: identifying, based on the custom adapterassociated with the particular data source, a predefined querytranslation format; and applying the identified predefined querytranslation format to the particular selected entity and the selectedsubset of the presented set of attributes to generate a translated queryin the predefined query translation format.
 4. The method of claim 1,wherein each custom adapter is uniquely generated at design time.
 5. Themethod of claim 1, wherein obtaining the set of data source informationand the set of metadata associated with the particular data sourcecomprises: identifying, via the query builder UI, a data source URL anda metadata URL from the user, wherein the data source URL is associatedwith the set of data source information and the metadata URL isassociated with the set of metadata associated with the particular datasource; and obtaining, via a web-based request, the set of data sourceinformation from the data source URL and the set of metadata from themetadata URL.
 6. The method of claim 1, further comprising, in responseto constructing the query: executing the constructed query against theparticular data source; and returning a query result set responsive toexecuting the constructed query via the query builder UI.
 7. The methodof claim 1, further comprising, in response to constructing the query:providing for presentation, via the query builder UI, an editableversion of the constructed query in the specified query format.
 8. Themethod of claim 1, further comprising, in response to obtaining the setof metadata associated with the particular data source: identifying,based on the custom adapter associated with the particular data source,a predefined entity metadata translation format; and translating the setof metadata associated with the particular data source using theidentified predefined entity metadata translation format associated withcustom adapter associated with the particular data source.
 9. The methodof claim 8, wherein a plurality of predefined entity metadatatranslation formats are available, each predefined entity metadatatranslation format associated with a metadata translation key, andwherein each custom adapter identifies a particular metadata translationkey to be used in translating the set of metadata associated with theparticular entity of the custom adapter.
 10. A system, comprising: atleast one processor; and a memory communicatively coupled to the atleast one processor, the memory storing instructions which, whenexecuted, cause the at least one processor to perform operationscomprising: identifying a particular data source associated with atleast one entity, each data source associated with a custom adapterassociated with a query builder framework, wherein each of the at leastone entities is associated with one or more attributes; obtaining a setof data source information defining each of the at least one entitiesand a set of metadata associated with the particular data source;providing for presentation, via a query builder user interface (UI)associated with the query builder framework, at least a portion of theat least one defined entities for selection by a user; in response toidentifying a selection of a particular entity via the query builder UI,providing for presentation, via the query builder UI, a set ofattributes associated with the particular selected entity for selectionby the user, wherein the set of attributes are determined based on theset of obtained metadata associated with the particular data source andassociated with the particular selected entity; and in response toidentifying a selection of a subset of the presented set of attributesvia the query builder UI by the user, constructing a query based on theparticular selected entity and the selected subset of the presented setof attributes in a specified query format associated with the customadapter associated with the particular data source, wherein the customadapter includes a set of query translation data providing the querybuilder framework with instructions on how to construct the querydirected to the particular data source, and wherein the specified queryformat is applied to the particular selected entity and the selectedsubset of the presented set of attributes to generate the query thatmeets format and syntax requirements of the data source.
 11. The systemof claim 10, wherein the particular data source is identified inresponse to a selection by the user from a plurality of data sources,and wherein each custom adapter is uniquely generated by a developer atdesign time.
 12. The system of claim 10, wherein each custom adapter isassociated with a query format specific to the associated data source,and wherein constructing the query based on the particular selectedentity and the selected subset of the presented set of attributes in thespecified query format comprises: identifying, based on the customadapter associated with the particular data source, a predefined querytranslation format; and applying the identified predefined querytranslation format to the particular selected entity and the selectedsubset of the presented set of attributes to generate a translated queryin the predefined query translation format.
 13. A non-transitorycomputer-readable medium storing instructions which, when executed,cause at least one processor to perform operations comprising:identifying a particular data source associated with at least oneentity, each data source associated with a custom adapter associatedwith a query builder framework, wherein each of the at least oneentities is associated with one or more attributes; obtaining a set ofdata source information defining each of the at least one entities and aset of metadata associated with the particular data source; providingfor presentation, via a query builder user interface (UI) associatedwith the query builder framework, at least a portion of the at least onedefined entities for selection by a user; in response to identifying aselection of a particular entity via the query builder UI, providing forpresentation, via the query builder UI, a set of attributes associatedwith the particular selected entity for selection by the user, whereinthe set of attributes are determined based on the set of obtainedmetadata associated with the particular data source and associated withthe particular selected entity; and in response to identifying aselection of a subset of the presented set of attributes via the querybuilder UI by the user, constructing a query based on the particularselected entity and the selected subset of the presented set ofattributes in a specified query format associated with the customadapter associated with the particular data source, wherein the customadapter includes a set of query translation data providing the querybuilder framework with instructions on how to construct the querydirected to the particular data source, and wherein the specified queryformat is applied to the particular selected entity and the selectedsubset of the presented set of attributes to generate the query thatmeets format and syntax requirements of the data source.
 14. Thecomputer-readable storage medium of claim 13, wherein the operationsfurther comprise: identifying, via the query builder UI, a data sourceURL and a metadata URL from the user, wherein the data source URL isassociated with the set of data source information and the metadata URLis associated with the set of metadata associated with the particulardata source; and obtaining, via a web-based request, the set of datasource information from the data source URL and the set of metadata fromthe metadata URL.
 15. The computer-readable storage medium of claim 13,wherein the operations further comprise: identifying, based on thecustom adapter associated with the particular data source, a predefinedentity metadata translation format; and translating the set of metadataassociated with the particular data source using the identifiedpredefined entity metadata translation format associated with customadapter associated with the particular data source.
 16. Thecomputer-readable storage medium of claim 13, wherein the operationsfurther comprise: executing the constructed query against the particulardata source; and returning a query result set responsive to executingthe constructed query via the query builder UI.
 17. Thecomputer-readable storage medium of claim 13, wherein the operationsfurther comprise: providing for presentation, via the query builder UI,an editable version of the constructed query in the specified queryformat.
 18. The computer-readable storage medium of claim 13, whereineach custom adapter is associated with a query format specific to theassociated data source, and wherein constructing the query based on theparticular selected entity and the selected subset of the presented setof attributes in the specified query format comprises: identifying,based on the custom adapter associated with the particular data source,a predefined query translation format; and applying the identifiedpredefined query translation format to the particular selected entityand the selected subset of the presented set of attributes to generate atranslated query in the predefined query translation format.